Skip to main content
Version: 2.0

AI And Automation Fundamentals

For two decades, I’ve watched technology reshape software development. But the current wave – fueled by advancements in AI and automation – feels different. It's not just what we build that's changing, but how we build it, and crucially, who does the building. As engineering leaders, we can’t afford to be passive observers. We need to proactively understand these forces, their implications for our teams, and how to strategically leverage them. This is about augmenting our teams, allowing engineers to focus on higher-value work.

This post will lay out some fundamentals, focusing not on the tech of AI (that’s a rabbit hole for another day) but on how to think about its impact as a leader, and how to prepare your team for this new reality.

Beyond the Buzzwords: What Does AI & Automation Really Mean for Engineering?​

The terms "AI" and "automation" are often thrown around interchangeably, but there's a subtle but important distinction.

  • Automation is about executing predefined tasks without human intervention. Think CI/CD pipelines, automated testing, or infrastructure-as-code. We’ve been doing this for years.
  • AI, particularly generative AI and large language models (LLMs), introduces a level of adaptability and learning that's new. It’s not just doing tasks; it's learning to do them better, and even handling tasks it wasn’t explicitly programmed for.

For engineering teams, this translates to a few key areas of impact:

  • Code Generation & Assistance: Tools like GitHub Copilot, MarsCode, and increasingly, IDE integrations, can generate code snippets, suggest completions, and even refactor existing code.
  • Testing & Bug Detection: AI can automate test case generation, identify potential bugs with greater accuracy, and even predict where issues might arise.
  • DevOps & Infrastructure Management: AI-powered tools can optimize resource allocation, automate incident response, and improve system reliability.
  • Documentation & Knowledge Management: AI can summarize complex documentation, answer technical questions, and create more accessible knowledge bases.

The Leadership Imperative: Shifting from “Doer” to “Orchestrator”​

The most significant challenge for engineering leaders isn’t understanding the technology itself, but adapting our leadership style. For many of us who came up as developers, the instinct is to jump in and do – to become power users of these new tools. While understanding is valuable, our primary role is shifting. We need to become orchestrators - guiding our teams through this transition, identifying the right opportunities for automation, and fostering a culture of experimentation.

Here’s what that looks like in practice:

  • Focus on Defining the “What”, Not Just the “How”: Instead of prescribing how a task should be done, focus on clearly defining the desired outcome. This empowers your team to leverage AI tools and find the most efficient approach.
  • Encourage Experimentation & Learning: Create a safe space for your team to experiment with AI tools, even if it means accepting occasional failures. Dedicate time for “AI Fridays” or similar initiatives where engineers can explore new technologies.
  • Invest in Upskilling: While AI can automate certain tasks, it also creates new opportunities for engineers to develop skills in areas like prompt engineering, AI model evaluation (tools like Arize AX, Braintrust, and Phoenix provide platforms for monitoring model performance, identifying biases, and ensuring reliability), and data science.
  • Establish Clear Guidelines & Governance: As AI tools become more integrated into our workflows, we need to address issues like code quality, security, and intellectual property. Establishing these guidelines sets the stage for effective training. We need to establish clear guidelines for how these tools should be used and how the resulting code will be reviewed.

Beyond Productivity: Reclaiming Time for Strategic Work​

The promise of AI and automation isn't just about doing more with less; it's about freeing up engineers to focus on more strategic work – the things that truly differentiate our products and drive innovation. Consider the story of a team I worked with who automated their regression testing suite using AI-powered tools. This freed up two senior engineers to focus on architecting a critical new feature, ultimately accelerating delivery by several weeks.

Think about the tedious, repetitive tasks that currently consume a significant portion of your team’s time: writing boilerplate code, manually testing features, triaging bug reports. These are prime candidates for automation. By offloading these tasks to AI, you can empower your engineers to focus on higher-level thinking and creative problem-solving.

The Long View: Adapting to a Continuously Evolving Landscape​

AI isn't a destination; it's a journey. The technology is evolving at a rapid pace, and we need to be prepared to adapt our strategies and approaches accordingly. This means staying informed about the latest advancements, experimenting with new tools, and fostering a culture of continuous learning.

This transition won’t happen overnight, and it will require investment in training and experimentation. As a leader, your role is to help your team navigate this ever-changing landscape and embrace the opportunities that AI and automation present. It’s about building a resilient, adaptable team that can thrive in a world where technology is constantly disrupting the status quo.

This isn’t about fearing the machine; it’s about harnessing its power to build a better future for our teams and our products.